mcpbeat

Make PR

posthog/make pr

> Create a GitHub pull request for the current branch using the gh CLI. Use when a user wants to open a PR and have the title, body, template, and assignee handled for them, following the repo's conventions and keeping public PRs free of PII.

307 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
0
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/PostHog/community-skills --skill Make PR

The instruction itself

3 sections, as written by the author

Make PR

Create a GitHub pull request for the current branch using the gh CLI.

Steps

  • Check for a PR template at .github/PULL_REQUEST_TEMPLATE.md or .github/pull_request_template.md. If found, follow its structure.
  • Run git log and git diff against the base branch to understand all changes.
  • Write a concise PR title (under 70 chars) and body. No emojis. Follow the repo template.
  • Discover the current user with gh api user --jq '.login' and assign them as the PR assignee.
  • Create the PR using gh pr create with --assignee.
  • Return the PR URL.

Rules

  • No filler, no emojis.
  • Push the branch first if not pushed: git push -u origin HEAD.
  • Use a HEREDOC for the PR body.
  • No PII or sensitive data — PRs are public.

How to use it

Copy the folder

Take posthog/make pr from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.